Provide output reponsive to proximate user input

ABSTRACT

One embodiment provides a method, including: receiving, at an information handling device, voice input; determining, using at least one sensor associated with the information handling device, whether the voice input comprises voice input provided proximate to the information handling device; and providing, based on determining that the voice input is provided proximate to the information handling device, output responsive to the voice input. Other aspects are described and claimed.

BACKGROUND

Information handling devices (“devices”), for example smart phones,tablet devices, smart speakers, laptop and personal computers, and thelike, may be capable of receiving command inputs and providing outputsresponsive to the inputs. A common method of providing input to a deviceis by providing voice input to the device (e.g., to a voice input moduleembodied in a personal assistant, etc.). Generally, regardless of thesource of the voice input (e.g., a proximate human user, anothernon-human source, etc.), a device may process the received input andprovide a responsive output.

BRIEF SUMMARY

In summary, one aspect provides a method, comprising: receiving, at aninformation handling device, voice input; determining, using at leastone sensor associated with the information handling device, whether thevoice input comprises voice input provided proximate to the informationhandling device; and providing, based on determining that the voiceinput is provided proximate to the information handling device, outputresponsive to the voice input.

Another aspect provides an information handling device, comprising: atleast one sensor; a processor; a memory device that stores instructionsexecutable by the processor to: receive voice input; determine whetherthe voice input comprises voice input provided proximate to theinformation handling device; and provide, based on determining that thevoice input is provided proximate to the information handling device,output responsive to the voice input.

A further aspect provides a product, comprising: a storage device thatstores code, the code being executable by a processor and comprising:code that receives voice input; code that determines whether the voiceinput comprises voice input provided proximate to the informationhandling device; and code that provides, based on determining that thevoice input is associated with a user proximate to the informationhandling device; output responsive to the voice input.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example of information handling device circuitry.

FIG. 2 illustrates another example of information handling devicecircuitry.

FIG. 3 illustrates an example method of providing output responsive todetermining that voice input was provided by a proximate user.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearance of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well knownstructures, materials, or operations are not shown or described indetail to avoid obfuscation.

Users frequently utilize devices to execute a variety of differentcommands or queries. One method of interacting with a device is to usedigital assistant software employed on the device (e.g., Siri® forApple®, Cortana® for Windows®, Alexa® for Amazon®, etc.). Digitalassistants are able to provide outputs (e.g., audible outputs, visualoutputs, etc.) that are responsive to a variety of different types ofuser inputs (e.g., voice inputs, etc.).

Conventionally, in regards to audio input, digital assistants mayprovide a corresponding output responsive to recognizing a command orquery present in the audio input, regardless of the source of the input.More specifically, conventional digital assistants are unable todifferentiate between a proximate human source (e.g., a user in the sameroom as the digital assistant, etc.) and a remote or non-human source(e.g., audible input provided by a television, etc.). For example, adigital assistant disposed in the same room as a television may processand provide output in response to audible input received from acommercial playing on the television (e.g., where the commercial recitesa trigger or wake word that activates the digital assistant, etc.). Thelack of an ability to differentiate between these types of inputs maylead to a variety of issues. For example, the production of unrequestedaudible output may be annoying to users in proximity to the digitalassistant.

Existing solutions claim to be able to differentiate between these typesof sources by distinguishing human vocal chords from electro-mechanicalspeakers. However, these solutions are largely unproven and are notimplemented in major digital assistant technologies.

Accordingly, an embodiment provides a method for providing outputresponsive to determining that voice input was provided by a proximatehuman user. In an embodiment, voice input (e.g., voice command input,voice query input, etc.) may be received at a device. An embodiment maythen use at least one sensor associated with the device (e.g., a thermalsensor, an audio capture device, an image capture device, etc.) todetermine if the voice input is associated with a proximate user (e.g.,a human user in the same room as the device, a human user within apredetermined distance of the device, etc.). Responsive to determiningthat the voice input is associated with a user proximate to the device,an embodiment may process the voice input and/or provide a responsiveoutput. Such a method may enable devices to differentiate betweenaudible input received from human sources and non-human sources andcorrespondingly ignore input from the latter.

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to smart phone and/or tabletcircuitry 100, an example illustrated in FIG. 1 includes a system on achip design found for example in tablet or other mobile computingplatforms. Software and processor(s) are combined in a single chip 110.Processors comprise internal arithmetic units, registers, cache memory,busses, I/O ports, etc., as is well known in the art. Internal bussesand the like depend on different vendors, but essentially all theperipheral devices (120) may attach to a single chip 110. The circuitry100 combines the processor, memory control, and I/O controller hub allinto a single chip 110. Also, systems 100 of this type do not typicallyuse SATA or PCI or LPC. Common interfaces, for example, include SDIO andI2C.

There are power management chip(s) 130, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 140, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 110, is usedto supply BIOS like functionality and DRAM memory.

System 100 typically includes one or more of a WWAN transceiver 150 anda WLAN transceiver 160 for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additionally, devices 120 are commonly included, e.g., an imagesensor such as a camera, audio capture device such as a microphone, athermal sensor, etc. System 100 often includes a touch screen 170 fordata input and display/rendering. System 100 also typically includesvarious memory devices, for example flash memory 180 and SDRAM 190.

FIG. 2 depicts a block diagram of another example of informationhandling device circuits, circuitry or components. The example depictedin FIG. 2 may correspond to computing systems such as the THINKPADseries of personal computers sold by Lenovo (US) Inc. of Morrisville,N.C., or other devices. As is apparent from the description herein,embodiments may include other features or only some of the features ofthe example illustrated in FIG. 2.

The example of FIG. 2 includes a so-called chipset 210 (a group ofintegrated circuits, or chips, that work together, chipsets) with anarchitecture that may vary depending on manufacturer (for example,INTEL, AMD, ARM, etc.). INTEL is a registered trademark of IntelCorporation in the United States and other countries. AMD is aregistered trademark of Advanced Micro Devices, Inc. in the UnitedStates and other countries. ARM is an unregistered trademark of ARMHoldings plc in the United States and other countries. The architectureof the chipset 210 includes a core and memory control group 220 and anI/O controller hub 250 that exchanges information (for example, data,signals, commands, etc.) via a direct management interface (DMI) 242 ora link controller 244. In FIG. 2, the DMI 242 is a chip-to-chipinterface (sometimes referred to as being a link between a “northbridge”and a “southbridge”). The core and memory control group 220 include oneor more processors 222 (for example, single or multi-core) and a memorycontroller hub 226 that exchange information via a front side bus (FSB)224; noting that components of the group 220 may be integrated in a chipthat supplants the conventional “northbridge” style architecture. One ormore processors 222 comprise internal arithmetic units, registers, cachememory, busses, I/O ports, etc., as is well known in the art.

In FIG. 2, the memory controller hub 226 interfaces with memory 240 (forexample, to provide support for a type of RAM that may be referred to as“system memory” or “memory”). The memory controller hub 226 furtherincludes a low voltage differential signaling (LVDS) interface 232 for adisplay device 292 (for example, a CRT, a flat panel, touch screen,etc.). A block 238 includes some technologies that may be supported viathe LVDS interface 232 (for example, serial digital video, HDMI/DVI,display port). The memory controller hub 226 also includes a PCI-expressinterface (PCI-E) 234 that may support discrete graphics 236.

In FIG. 2, the I/O hub controller 250 includes a SATA interface 251 (forexample, for HDDs, SDDs, etc., 280), a PCI-E interface 252 (for example,for wireless connections 282), a USB interface 253 (for example, fordevices 284 such as a digitizer, keyboard, mice, cameras, phones,microphones, storage, other connected devices, etc.), a networkinterface 254 (for example, LAN), a GPIO interface 255, a LPC interface270 (for ASICs 271, a TPM 272, a super I/O 273, a firmware hub 274, BIOSsupport 275 as well as various types of memory 276 such as ROM 277,Flash 278, and NVRAM 279), a power management interface 261, a clockgenerator interface 262, an audio interface 263 (for example, forspeakers 294), a TCO interface 264, a system management bus interface265, and SPI Flash 266, which can include BIOS 268 and boot code 290.The I/O hub controller 250 may include gigabit Ethernet support.

The system, upon power on, may be configured to execute boot code 290for the BIOS 268, as stored within the SPI Flash 266, and thereafterprocesses data under the control of one or more operating systems andapplication software (for example, stored in system memory 240). Anoperating system may be stored in any of a variety of locations andaccessed, for example, according to instructions of the BIOS 268. Asdescribed herein, a device may include fewer or more features than shownin the system of FIG. 2.

Information handling device circuitry, as for example outlined in FIG. 1or FIG. 2, may be used in devices such as tablets, smart phones, smartspeakers, personal computer devices generally, and/or electronic deviceswhich may include digital assistants that a user may interact with andthat may perform various functions responsive to receiving user input.For example, the circuitry outlined in FIG. 1 may be implemented in atablet or smart phone embodiment, whereas the circuitry outlined in FIG.2 may be implemented in a personal computer embodiment.

Referring now to FIG. 3, an embodiment may provide output responsive todetermining that voice input was provided by a proximate user. At 301,an embodiment may receive voice input from at least one user. The voiceinput may be any type of input such as a command input, query input, andthe like. In an embodiment, the voice input may be received at an inputdevice (e.g., a microphone, a speech capture device, etc.) operativelycoupled to a speech recognition device.

In an embodiment, the input device may be an input device integral tothe speech recognition device. For example, a smart phone may bedisposed with a microphone capable of receiving voice input data.Alternatively, the input device may be disposed on another device andmay transmit received voice input data to the speech recognition device.For example, voice input may be received at a smart speaker that maysubsequently transmit the voice data to another device (e.g., to auser's smartphone for processing, etc.). Voice input data may becommunicated from other sources to the speech recognition device via awireless connection (e.g., using a BLUETOOTH connection, near fieldcommunication (NFC), wireless connection techniques, etc.), a wiredconnection (e.g., the device is coupled to another device or source,etc.), through a connected data storage system (e.g., via cloud storage,remote storage, local storage, network storage, etc.), and the like.

In an embodiment, the input device may be configured to continuouslyreceive voice input data by maintaining the input device in an activestate. The input device may, for example, continuously detect voiceinput data even when other sensors (e.g., cameras, light sensors,speakers, other microphones, etc.) associated with the speechrecognition device are inactive. Alternatively, the input device mayremain in an active state for a predetermined amount of time (e.g., 30minutes, 1 hour, 2 hours, etc.). Subsequent to not receiving any voiceinput data during this predetermined time window, an embodiment mayswitch the input device to a power off state. The predetermined timewindow may be preconfigured by a manufacturer or, alternatively, may beconfigured and set by one or more users.

At 302, an embodiment may determine if the voice input is associatedwith a user proximate to the speech recognition device. In anembodiment, the determination may be made by utilizing at least one of avariety of different sensors such a thermal sensor (e.g., a thermopilesensor, etc.), an image capture device (e.g., a camera, etc.), an audiocapture device (e.g., a microphone, etc.), and the like. Data obtainedfrom one or more of these sensors may be used in the determination. Inan embodiment, the sensors may be integral to the device or,alternatively, may be disposed on another device and may transmit data(e.g., using a wired or wireless connection, etc.) to the device. Thedata from the sensors disposed on another device may be communicatedfrom other sources to the device via a wireless connection (e.g., usinga BLUETOOTH connection, near field communication (NFC), wirelessconnection techniques, etc.), a wired connection (e.g., the device iscoupled to another device or source, etc.), through a connected datastorage system (e.g., via cloud storage, remote storage, local storage,network storage, etc.), and the like. The data attained from the sensorsmay be used to determine whether the voice input was provided by a userin the vicinity of the device or, alternatively, provided by anothersource (e.g., a remote source such as a television commercial, etc.).

In an embodiment, the at least one sensor may be a thermal sensor. Anembodiment may detect thermal data associated with a proximate user byutilizing the thermal sensor. In this context, thermal data may refer toheat data emitted by a thermal entity (e.g., a proximate human user,etc.). In an embodiment, the thermal data may be detected by at leastone thermal sensor associated with a device. The thermal sensor may be asensor integral to the device. For example, a smart phone may bedisposed with a thermal sensor capable of detecting heat signatures ofsurrounding thermal entities. Alternatively, the thermal sensor may bedisposed on another device and may transmit detected thermal data to thedevice. For example, a smart thermostat in the same room as the speechrecognition device may be disposed with a thermal sensor that may detectnearby thermal data and subsequently transmit that data to the speechrecognition device. An embodiment may determine that voice input isassociated with a proximate user if thermal data associated with theproximate user is detected substantially when, or shortly after (e.g.,within a predetermined time threshold such as 1 second, 2 second, etc.),voice input is received by the device. In an embodiment, the thermalsensor may be a 1-pixel thermal sensor comprising a lens positioned infront of the thermal sensor. The lens may help to differentiatedifferent thermal objects in its field of view. For example, if twothermal objects are detected and one of the objects is very hot and theother is not, the very hot object may saturate the 1-pixel sensor andobscure the colder object. Therefore, the lens may help to smooth thisout by requiring or mixing the heat sensing across a wider area.Additionally, the lens may help to differentiate between a thermalentity associated with a pet and a thermal entity associated with aperson by “forcing” the sensor to “see” at a given height, or across arange of heights.

In an embodiment, the at least one sensor may be an image capturedevice. An embodiment may detect image data associated with a proximateuser by utilizing the image capture device. In this context, image datamay refer to still image data (e.g., a photo, etc.) and/or moving imagedata (e.g., a video, etc.). In an embodiment, detected images may becompared to stored image data (e.g. image data stored in a database,etc.) and/or accessible image data (e.g., image data accessible online,etc.), where the stored and/or accessible image data is associated withimages of human users. Based on the comparison, an embodiment maydetermine whether the detected image data is associated with a humanuser. For the comparison, an embodiment may utilize any image data itdetected substantially when, or shortly before or after, voice input wasreceived. In another embodiment, responsive to receiving voice input, anembodiment may initiate instructions to capture image data, which maythen be used for the comparison.

In an embodiment, the at least one sensor may be an audio capturedevice. An embodiment may detect audio data associated with a proximateuser by utilizing the audio capture device. In this context, audio datamay refer to various types of voice inputs such as vocal command inputs,vocal query inputs, and the like. In an embodiment, a direction theaudio input was provided from may be determined. For example, utilizingknown sound localization techniques, an embodiment may be able toidentify the direction of the audible input. Using this identifieddirection, an embodiment may be able to determine whether the audibleinput was provided by a proximate human user or another, non-humansource. For example, if a device knows the location of other proximatedevices (e.g., from previous user inputs, by communicating with theother devices, etc.), responsive to receiving audible input anembodiment may be able to identify the direction of the source of theinput and determine if that source is associated with the location ofone of the other proximate devices. If an embodiment identifies that theaudible input derived from a location associated with a proximate devicethen an embodiment may conclude that the source of the input was theproximate device and not a human user.

Additional methods of determining whether voice input is associated witha user may be utilized. In an embodiment, speaker recognition may beutilized. For example, an embodiment may analyze the voice input todetermine characteristics associated with the voice input (e.g., usingknown voice analysis techniques such as spectrogram analysis, speechparsing, etc.) and attempt to identify a user and/or a voice profileassociated with a user by using the determined voice inputcharacteristics. If the speaker is unknown, an embodiment may ignore thevoice input. In another embodiment, an embodiment may identifydevice-associated output such as commercials. For example, an embodimentmay receive audio input and determine that the input is associated witha commercial (e.g., by accessing a database of known commercials, usingaudio identifying technology like Shazam®, etc.). Responsive toidentifying that the audio input is associated with a commercial, anembodiment may ignore the input. In yet another embodiment, anembodiment may identify device-associated audio input by recognizinghidden or masked tones in a media stream, such as the signaling includedin some ratings tracking systems. In yet another embodiment, speakerdiarization techniques and signal processing, such as blind sourceseparation, may also be used to determine whether audible input isassociated with a human user or another device. In yet anotherembodiment, an embodiment may snoop on casted traffic. Moreparticularly, by knowing the audio that is being played by speakers, thesystem can perform an AEC-like signal processing technique to remove thesignal from the microphone stream.

All of the aforementioned methods may be used individually or incombination to determine whether voice input is associated with a user.

Responsive to determining, at 302, that the voice input is associatedwith a user proximate to the device, an embodiment may provide, at 304,output responsive to the voice input. The output may be audio output,visual output, a combination thereof, or the like. In an embodiment, theaudible output may be provided through a speaker, another output device,and the like. In an embodiment, the visual output may be providedthrough a display screen, another display device, and the like. In anembodiment, the output device may be integral to the speech recognitiondevice or may be located on another device. In the case of the latter,the output device may be connected via a wireless or wired connection tothe speech recognition device. For example, a smart phone may provideinstructions to provide audible output through an operatively coupledsmart speaker. In an embodiment, output may refer to other types ofoutput that do not have an audible or visual effect (e.g., processingoutput, transaction output, etc.).

An embodiment may utilize a threshold based on the content or context ofthe audible input query/command. An embodiment may assign confidencescores to all received input and only process and/or provide outputresponsive to the inputs that are greater than the threshold. In anembodiment, the threshold may be a variable threshold that may changebased on the type of output requested to be performed by the input. Forexample, the threshold level may be higher if the request is to performsome physical action, is related to a financial transaction, is relatedto personal information, warrants a lengthy response, and the like.

Responsive to determining, at 302, that the voice input is notassociated with a user proximate to the device, an embodiment may, at303, take no action. For example, in an embodiment, the received voiceinput may be ignored. In another example, an embodiment may receive thevoice input but, based on the determination, choose not to process thevoice input and/or choose not to provide output responsive to the voiceinput. In yet another example, an embodiment may provide a clarificationquery requesting that a user provide a confirmation input to confirm thevoice input. If no confirmation input is received within a predeterminedtime threshold (e.g., 10 seconds, 15 seconds, etc.) an embodiment mayignore the voice input. If confirmation input is received within thepredetermined time threshold, then an embodiment may, at 304, provideresponsive output.

The various embodiments described herein thus represent a technicalimprovement to conventional input source identification techniques.Using the techniques described herein, an embodiment may determinewhether received audible input is associated with a proximate human useror is associated with a non-human source. If an embodiment determinesthat the input is associated with a non-human source, then an embodimentmay ignore the input and/or provide no output. Such techniques prevent adevice from processing and providing output responsive to input notprovided by a human user.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device that are executed by aprocessor. A storage device may be, for example, a system, apparatus, ordevice (e.g., an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus, or device) or any suitablecombination of the foregoing. More specific examples of a storagedevice/medium include the following: a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a magnetic storage device, or any suitablecombination of the foregoing. In the context of this document, a storagedevice is not a signal and “non-transitory” includes all media exceptsignal media.

Program code embodied on a storage medium may be transmitted using anyappropriate medium, including but not limited to wireless, wireline,optical fiber cable, RF, et cetera, or any suitable combination of theforegoing.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made through other devices (for example, throughthe Internet using an Internet Service Provider), through wirelessconnections, e.g., near-field communication, or through a hard wireconnection, such as over a USB connection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and program products accordingto various example embodiments. It will be understood that the actionsand functionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, a special purpose information handling device, or otherprogrammable data processing device to produce a machine, such that theinstructions, which execute via a processor of the device implement thefunctions/acts specified.

It is worth noting that while specific blocks are used in the figures,and a particular ordering of blocks has been illustrated, these arenon-limiting examples. In certain contexts, two or more blocks may becombined, a block may be split into two or more blocks, or certainblocks may be re-ordered or re-organized as appropriate, as the explicitillustrated examples are used only for descriptive purposes and are notto be construed as limiting.

As used herein, the singular “a” and “an” may be construed as includingthe plural “one or more” unless clearly indicated otherwise.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

1. A method, comprising: receiving, at an information handling device,voice input; determining, using at least one sensor associated with theinformation handling device, whether the voice input comprises voiceinput provided by a proximate human source or a non-human source; andproviding, based on determining that the voice input is provided by aproximate human source, output responsive to the voice input.
 2. Themethod of claim 1, wherein the determining comprises determining thatthe voice input is provided by a human source proximate to theinformation handling device.
 3. The method of claim 1, wherein the atleast one sensor is not disposed on the device.
 4. The method of claim1, wherein the at least one sensor comprises at least one thermal sensorand wherein the determining comprises detecting, using the at least onethermal sensor, thermal data.
 5. The method of claim 4, wherein theproviding comprises providing output if the thermal data is determinedto be associated with a user proximate to the information handlingdevice.
 6. The method of claim 1, wherein the at least one sensorcomprises at least one image capture device and wherein the determiningcomprises detecting, using the at least one image capture device, imagedata.
 7. The method of claim 6, wherein the providing comprisesproviding output if the image data is associated with the user proximateto the information handling device.
 8. The method of claim 1, whereinthe at least one sensor comprises at least one audio capture device andwherein the determining comprises determining a direction of audioreceived by the audio capture device and further comprising notproviding output if the direction is associated with another device. 9.The method of claim 1, wherein the determining comprises determiningthat the voice input is not provided proximate to the informationhandling device and further comprising not providing output.
 10. Themethod of claim 1, wherein the determining comprises a threshold andwherein the providing comprises providing output if the determinationthat the voice input is associated with the user proximate to theinformation handling device is greater than the threshold.
 11. Aninformation handling device, comprising: at least one sensor; aprocessor; a memory device that stores instructions executable by theprocessor to: receive voice input; determine whether the voice inputcomprises voice input provided by a proximate human source or anon-human source; and provide, based on determining that the voice inputis provided by a proximate human source, output responsive to the voiceinput.
 12. The information handling device of claim 11, wherein toreceive voice input comprises instructions executable by the processorto receive voice input from a sensor associated with another device. 13.The information handling device of claim 11, wherein the at least onesensor comprises at least one thermal sensor and wherein theinstructions executable by the processor to determine compriseinstructions executable by the processor to detect, using the at leastone sensor, thermal data.
 14. The information handling device of claim13, wherein the instructions executable by the processor to providecomprise instructions executable by the processor to provide output ifthe thermal data is determined to be associated with a user proximate tothe information handling device.
 15. The information handling device ofclaim 11, wherein the at least one sensor comprises at least one imagecapture device and wherein the instructions executable by the processorto determine comprise instructions executable by the processor todetect, using the at least one image capture device, image data.
 16. Theinformation handling device of claim 15, wherein the instructionsexecutable by the processor to provide comprise instructions executableby the processor to provide output if the image data is associated withthe user proximate to the information handling device.
 17. Theinformation handling device of claim 11, wherein the at least one sensorcomprises at least one audio capture device and wherein the instructionsexecutable by the processor to determine comprise instructionsexecutable by the processor to determine a direction of audio receivedby the audio capture device and wherein the instructions are furtherexecutable by the processor to not provide output if the direction isassociated with another device.
 18. The information handling device ofclaim 11, wherein the instructions executable by the processor todetermine comprise instructions executable by the processor to determinethat the voice input is not provided proximate to the informationhandling device and wherein the instructions are further executable bythe processor to not provide output.
 19. The information handling deviceof claim 11, wherein the instructions executable by the processor todetermine comprise a threshold and wherein the instructions executableby the processor to provide comprise instructions executable by theprocessor to provide output if the determination that the voice input isassociated with the user proximate to the information handling device isgreater than the threshold.
 20. A product, comprising: a storage devicethat stores code, the code being executable by a processor andcomprising: code that receives voice input; code that determines whetherthe voice input comprises voice input provided by a proximate humansource or a non-human source; and code that provides, based ondetermining that the voice input is provided by a proximate humansource; output responsive to the voice input.